Supported Locking Criteria

Sentinel RMS supports the following hardware and software-based license locking criteria on different platforms.

NOTE   From Sentinel RMS v9.7 onwards, Linux ARM operating system is supported.

Criteria | Hex | Description Windows Linux Mac Solaris Sparc Solaris x86 AIX HPUX Android Linux ARM
ID PROM (0x001)
Processor serial number or ID		 NA 7 NA NA

IP Address (0x002)
Network address of computer in IPv4 format. License locking to IPv6 addresses is not supported5

 NA
Disk ID (0x004)
Value derived from the hard drive volume serial number (operating system assigned) on Windows. For non-Windows, Disk ID is the value derived from system directories and their I-Node values.		 NA
Host Name (0x008)
Name of the host		 NA
Ethernet Address (0x010)
Unique Ethernet card ID		 1 1 NA
Computer ID Key (0x080)
Hardware protection device		 9 2,9 NA NA NA NA NA NA NA
Hard Disk Serial (0x800)6
Value derived from the hard drive (software vendor assigned) serial number		 10 3 8 4 4 NA NA NA NA

CPU Info String (0x1000)

Traditional locking criteria (listed above) are generally not considered reliable in virtual environments. In certain cases, a virtual environment may not even support the chosen traditional locking option. Therefore, CPU info-based locking is useful for licensing applications on virtual machine workstations. However, you must combine this locking criteria with other network and system identifiers, such as Ethernet address and IP address.

Refer to:

Fingerprinting in Single Host VM Environments

NA NA NA NA NA

UUID (0x2000)
Useful for licensing applications on VMware ESX and ESXi clusters. However, you must combine this locking criteria with other network and system identifiers, such as Ethernet address and IP address.

Refer to:

Fingerprinting in Clustered VM Environments

3 NA NA 3 NA NA NA NA
Standard Custom (0x100)
Defined by your application
Extended Custom (0x400)
Defined by your application		 (Recommended)

1 Multiple NICs are not supported on Solaris currently.

2 Computer ID Key is supported on Ubuntu from Sentinel RMS v9.3.0 onwards.

3 Root/administrative privileges are required to obtain locking information for this criteria.

4 The kstat library (libkstat.so) must be present on the Solaris system and the kstat command must obtain the hard disk serial number.

5 License locking for IPv6 addresses is not supported. Consequently, the locking code generators (like, echoid and rcommute) cannot generate IPv6-based locking codes even if the LSTCPIPVER environment variable is set to 6 (means IPv6). In the case of a dual stack system, IPv4 locked licenses will be supported in IPv4 as well as IPv6 mode.

6 Sentinel RMS does not support hard disk serial as a locking criterion for virtual machines.

7 IDPROM returns the value of the host id. If host id is not found, then the hexadecimal equivalent of the IPV4 address of the machine is returned.

8 For Hard Disk Serial, the supported physical interconnects are AIX, SATA, SCSI, ATAPI, and Apple Fabric.
9 When Computer ID key is used as the sole locking criteria, the lock code is not verified when the license is loaded onto a standalone or network server.

10 In the case of Sentinel RMS version 10.0.0 or earlier, same privileges must be used for obtaining Hard Disk Serial-based fingerprints and using the licensed applications. From 10.0 onwards, there is no such limitation.